Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Partially revert Samsung keyboard force-update workaround#17391

Merged
GaryQian merged 2 commits into
flutter-team-archive:masterfrom
GaryQian:samsungrevert
Mar 29, 2020
Merged

Partially revert Samsung keyboard force-update workaround#17391
GaryQian merged 2 commits into
flutter-team-archive:masterfrom
GaryQian:samsungrevert

Conversation

@GaryQian

Copy link
Copy Markdown
Contributor

Reverts the functional part of #16547

Leaves the testing improvements and samsung keyboard filtering portion of the original PR intact.

@GaryQian GaryQian requested a review from tvolkert March 29, 2020 21:03
@auto-assign auto-assign Bot requested a review from gw280 March 29, 2020 21:03
@GaryQian GaryQian removed the request for review from gw280 March 29, 2020 21:03
@tvolkert

Copy link
Copy Markdown
Contributor

So from your comment on #16547, does this mean that this PR will re-introduce flutter/flutter#31512?

@GaryQian

Copy link
Copy Markdown
Contributor Author

It will reintroduce parts of that bug on some devices. flutter/flutter#31512 turned out to be a really wide bug covering a bunch of different behaviors.

@GaryQian

Copy link
Copy Markdown
Contributor Author

It looks like the new breakage is worse than the ones this fixed though, so we can revert for now. I am currently/already/in the process of exploring other approaches to resolve these bugs.

@tvolkert

Copy link
Copy Markdown
Contributor

Sounds good - thanks!

@tvolkert

Copy link
Copy Markdown
Contributor

Linking back to bug: flutter/flutter#53086

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Development

Successfully merging this pull request may close these issues.

3 participants